ziggy build - accept target argument#161
Merged
louismerlin merged 2 commits intomainfrom Apr 13, 2026
Merged
Conversation
Adapt target resolving, such that guessing fails when bin target is non-unique. Additionally, cache `cargo_metadata` in `Common` struct (now an argument for every subcmd).
chris-srlabs
force-pushed
the
feat-build-target
branch
from
889520b to
143ef97
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Do not build all targets, but only those specified (or resolved), this implicitly propagates to the fuzz subcmd.
Usually the harness contains a single bin target and then nothing changes. This errs before building and trying to fuzz a non existing target. Avoid confusion, by resolving the target automatically only when unambiguous.
Additionally, cache
cargo_metadatainCommonstruct (now an argument for every subcmd).builds on #158